Method of enabling a wireless information device to access location data

ABSTRACT

A method of enabling a first wireless information device to access absolute location data in which the first wireless information device does not possess its own absolute location finding system but is instead able to receive, over a wireless network, absolute location data from a second wireless information device that does have its own absolute location finding system. The present invention hence enables wireless information devices to share absolute location data: for example, a mobile telephone with GPS capability can be used as a local “beacon” to broadcast its absolute location to any nearby devices over a personal area wireless network (e.g. a Bluetooth network) so that those nearby devices can use that location data. Hence, a camera with no location finding system of its own could obtain location data from a nearby GPS equipped mobile telephone over a Bluetooth PAN and watermark its images with location data.

BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention relates to a method of enabling a wireless informationdevice to access location data. The term ‘wireless information device’used in this patent specification should be expansively construed tocover any kind of device with one or two way wireless communicationcapabilities and includes without limitation radio telephones, smartphones, communicators, personal computers, computers and wirelessenabled application specific devices such as cameras, video recorders,asset tracking systems etc. It includes devices able to communicate inany manner over any kind of network, such as GSM or UMTS, CDMA and WCDMAmobile radio, Bluetooth, IrDA etc.

2. Description of the Prior Art

As mobile Internet devices and third generation mobile networks becomemore pervasive, location based services are thought to be a major growtharea. Providing information, context and services based on locationawareness enables the potential for new capabilities and simplifiedinterfaces for the user, as well as new revenue streams for operatorsand service providers.

The technology required for provision of automated location informationto mobile devices has been in continual development for several decades.Whilst the majority has its roots in military, naval and aviationapplications, modern consumer technology is also rising to meet thechallenges, specifically in the metropolitan environment. Typicalexamples of location technology that are being adopted for use inwireless information devices include GPS and basestation triangulationtechnology that can very accurately measure the time of signal arrival.A device able to determine its absolute location has, conventionally,had to include its own location finding components (e.g. a GPS receiverand related software). These location finding systems are usuallyregarded as establishing an “absolute location”; this means the physicallocation in an absolute reference frame, such as WGS-84, as opposed tological location (e.g. close to a specific location beacon).

Reference may be made to U.S. No. 2001/048746, which shows a mobiletelephone with GPS capabilities that is able to share GPS location datawith other devices over a short range wireless link; this obviates theneed for those other devices to have their own GPS capability.

SUMMARY OF THE PRESENT INVENTION

In a first aspect there is a method of enabling a first wirelessinformation device to access absolute geographic data (i.e. location,speed or direction), in which the first wireless information device docsnot possess its own absolute geographic finding system but is insteadable to receive, over a wireless network absolute geographic data from asecond wireless information device that does have its own absolutegeographic finding system; in which the second wireless informationdevice is programmed to enable any authorised component, whether runningon the second wireless device or the first wireless information device,to define quality of position parameters and to be sent location datafrom one or more absolute location finding systems running on the secondwireless information device that meet those parameters.

The present invention hence enables wireless information devices toshare absolute location data: for example, a mobile telephone with GPScapability can be used as a local ‘beacon’ so broadcast its absolutelocation to any nearby devices over a wireless PAN (personal areanetwork, e.g. a Bluetooth network) so that those nearby devices can usethat location data. Hence, a camera with no location finding system ofits own could obtain location data from a nearby GPS equipped mobiletelephone over a Bluetooth PAN and watermark its images with locationdata.

‘Absolute location’ In this context means the physical location in anabsolute reference frame, such as WGS-84, as opposed to logical location(e.g. close to a specific location beacon).

The second wireless information device could be a simple RF ID tag usedin asset tracking whenever the tag is dose enough to a device that isbroadcasting absolute location data it stores a second of that absolutelocation, hence building up a record of its journey.

The second wireless information device does not have to be a portabledevice, but may be a simple, fixed location beacon programmed with itsabsolute location. It may also be unable to independently obtain thatlocation, but be simply programmed with it (e.g. may be connected to aWAN and be sent its absolute location over that WAN).

Other kinds of data that accompany location data can also be sharedbetween the first and second devices across the wireless network forexample; if the second wireless information device has a GPS receiver,than not only are absolute location co-ordinates generated, but alsospeed and direction co-ordinates as well. With the present invention,any or all of absolute location, speed and direction (or indeed anyother absolute geographic indicator) can be shared between devices. Thepresent invention therefore introduces the concept of ‘distributedabsolute geographic awareness’—i.e. distributing or sharing absolutegeographic data: absolute location, speed in that absolute referenceframe used to establish location or direction in that absolute referenceframe (and any combination of the three). It hence leverages the abilityof just one device to actually obtain and that absolute geographic data,or of one device to obtain one kind of absolute geographic data, andanother device to obtain a different kind.

In a second aspect, there is a wireless information device programmedwith its own absolute geographic finding system and capable of sharingabsolute geographic data with a second wireless information device thatdoes not possess its own absolute geographic finding system but isinstead able to receive, over a wireless network, absolute geographicdata from the wireless information device; in which the wirelessinformation device is programmed to enable any authorised component,whether running on the device or the second device, to define quality ofposition parameters and to be sent location data from one or moreabsolute location finding systems running on the device that meet thoseparameter.

BRIEF DESCRIPTION OF THE DRAWING

The present invention will be described with reference to accompanyingdrawing FIG. 1, which shows an architecture for a wireless informationdevice that can implement the present investigation.

DETAILED DESCRIPTION

An implementation of the present invention enables absolute locationdata sharing between (a) any kind of device that is both cognisant ofits absolute location and is capable of transmitting that data locationand (b) any kind of wireless device that is capable of receiving thattransmitted location data and that might, for whatever reason, benefitfrom being able to use knowledge of its absolute location. In mostpractical implementations, the data transmission will be over atransient personal area wireless network, such as a Bluetooth network.Further, most mobile telephones will have some form of absolute locationfinding capability in the near future and hence make an ideal locationbeacon for transmitting absolute location data to nearby devices.

To give an indication of the breadth of potential applications of thepresent invention, the following further examples of use are given:

Use Cases

1. An interesting use case is that of enabling a MP3/Ogg Vorbis digitalmusic playing device to pick up a user's absolute location using thepresent invention (e.g. from that user's location enabled mobiletelephone) and to play a favourite song that reminds the user orconnects him to that location. This requires the music playing device tobe able to store and update a database with locations and music songsassociated with each location.

2. Another simpler idea is that when you take a photo with your camerait embeds a location fix in the postcard which can then be transmittedover the network using Obex that includes a location object in there.

3. Other use cases cover asset tracking and fleet management serviceswhere, for example, when a courier delivers a parcel, the signatoryeffectively watermarks its signature with the location of delivery. Forfleet management, a wireless information device could discover (orcalculate) it's position from the vehicle's on-board location system.

4. Another use case is that of location-relaying where many devices in a“wireless-chain”, relay the location fix obtained from an other. In thatscenario, only one such device can obtain the absolute location fix(from GPS or Galileo satellites for example) and the others relay it; sothat for example in a building many devices get to know about theirlocation together with an error which can be calculated from the numberof hops. In that scenario, triangulation is also possible using multiplesources.

5. An interesting use case is that of asset tracking with restrictedoperational range. For example if a laptop should not leave a predefinedarea/premises etc. Then it can be programmed to seek such locationbeacons and completely lock or destruct (automatically or aftercommunication to base) if such location identification is made. Thevalue there of that laptop (or other device for that matter) not to haveit's own location system is that it can pick up location beacons frommany other device and after authentication (or not) make the appropriatedecisions and actions.

6. As noted earlier, it is possible to share non-location data as well.For example, an on-car GPS navigation system could share speed data withto an on-car data recorder, that would alert the user if it's speed wasexcessive. The on-car data recorder could use location information fromthe GPS system to establish the road the car was travelling on (forexample, in conjunction with conventional GPS navigation software, suchas the TomTom Navigator) and, using a database of applicable speedlimits for all roads, establish if the car is speeding or not. The GPSnavigation system could also share location data with an on-car roadcharging system: the congestion charging system can work out if thecar's location corresponds to a charge area (e.g. toll road, congestionarea) and then ensure that the appropriate debit or charge or payment ismade.

The method used to share absolute location data is relativelystraightforward. For example, one way to distribute absolute locationinformation to the personal area network over Bluetooth is to havedevices inquiring the location-aware device's, SDP (service discoveryprotocol) records—using a universally unique identifier (UUID)—for theparticular service that provides the location information. In fact, thelocation-aware device can make this process much simpler and faster byincluding the location fix in it's SDP service records and thusreturning the result to the interested parties embedded in the SDPresponse (as opposed to returning the relevant info for the remotedevice to connect to the location service).

Another way (which would require more battery power) would be for aBluetooth device to periodically broadcast/multicast such location fixesusing raw Bluetooth Link Layer AUX packets and thus allow anyone whomight listen to pick them up.

A standardised location data format, akin to the vCard format forpersonal contact information, would be possible.

Currently, applications that need location information are tightly boundinto the technology that provides the location data. This may requiredevelopers to understand in detail how GPS and GSM triangulationlocation technologies operate, which is onerous. The present inventioncan be implemented using a location technology “insulation layer” in thesecond wireless information device OS which separates and hencedecouples applications and any system servers from the underlyinglocation technologies. Hence, location technologies (e.g. a GPS plug-inor a GSM triangulation plug-in) provide location data to the insulationlayer (a server in a Symbian OS implementation). This server insulationlayer then gives access to the location data to any client (e.g. anapplication or system server) that needs it over a generic API.Critically, the client need not be limited to a client on the secondwireless information device itself, but can reside on a completelydifferent device that does not have its own location finding system.

There are further advantages to a location insulation layer approach:

-   -   Application developers can develop location based apps without        needing to understand the specifics of any location technology        such as GPS or even define the kind of location technology that        should be providing the location data; they merely need to be        able to use the API.    -   Location technology developers can develop location technology        without needing to understand the specifics of any application        or system server; the location technology can be implemented as        plug-ins, which are potentially hot swappable;    -   Any application or resource on the device that needs location        data can now readily obtain it; location data is made available        across the entire OS.    -   Multiple location technologies could be running on one device,        with the insulation layer deciding which technology to use at        any time—the application need know nothing about a hot-swap over        between technologies;    -   The location information can be readily supplied to different        system servers—e.g. a system server which decided which        bearer/protocol to communicate over could be fed location        information and use that as part of its decision making; hence,        when within range of a Bluetooth pod, it could change to        Bluetooth; when out of range, it could revert to GSM etc.    -   A device can be readily made to dial out its location        information (e.g. to the police) if the device receives an        appropriate trigger message that the device is stolen.    -   A publish and subscribe API can be used to enable any such        authorised server, whether running on the second wireless        information device or the first wireless information device, to        subscribe to location data published by any of the location        finding systems running on the second wireless information        device

APPENDIX 1

Appendix 1 comprises a more detailed description of a suitablearchitecture, plus a discussion of some important design principles fora location aware operating system.

1. Source Data Processing

The location aware device can use one or more different location sensingtechnologies; where more than one is used, a technique for combininglocation data from multiple sources into a single estimate of locationmay be employed. This is particularly useful where the different sourceshave differing characteristics, in terms of acquisition technique andaccuracy. The aim of such processing is to improve the new accuracy of alocation fix, above that of any individual source.

Kalman filtering is often used to combine, GPS and INS data, as thestrengths of each compensate the weaknesses of the other very well,resulting in output data of higher accuracy than anyone of them canprovide at any given instant in time.

2. Security, Privacy

Security of location information is based around “Who”, “Where”, and“When”. These are listed in order of importance for protection. Thelocation aware device should guard the most securely whom it represents.“Where” that person is can reasonably be shared with others also in thelocality (although arguably so long as the “who” is not shared) asexplained above, and time can be shared with anyone (restricting theother two).

However, as this information is the most dangerous when more than one isknown (in particular, all three, and for a range of times), securing allthree, from leakage to remote parties, is the most sure-fire way ofavoiding this most sensitive combination falling into the wrong hands.So each of the three should only issued on a “need to know”basis—providing open services in a personal device should only be doneon the explicit instruction of the user.

3. Location Discovery vs. Navigation

Another way of partitioning services is between location discovery(static), and navigating through space (dynamic). A third class is theintersection of these two (continuously discovering whilst moving).

Discovery covers many areas, such as

-   -   1. Own location (“where am I?”)    -   2. Other location (“Where am I going?”)    -   3. Person location (“Buddy finder”)    -   4. Information filtering (“present traffic info before going out        of home on Monday morning”)    -   5. action/event filtering (‘don't beep loudly when in the cinema        or boss' office’)    -   6. Service location (“Find my nearest . . . ”)    -   7. Other property of a location (local time-zone, traffic        conditions, weather, etc.)

The last two are to many degrees interchangeable, as you can view alocal service as a property of a location, and a service may itselfprovide other information (properties) about that location.

4. Location Awareness: Architecture Considerations

App Engines

Location knowledge is primarily an application service, although it isimportant to appreciate that the applications that use the location datacan be distributed across several devices, connected over a wirelessPAN.

Contacts and Agenda applications can benefit greatly from location data,and there is also potential for journaling. Location based searching forlocal as well as remote content is facilitated. One could imagine a“location” stamp anywhere there is currently a “time” stamp—e.g. ondocuments (e.g. to establish where electronically signed; on photographsfor evidential reasons, with the location data being watermarked to betamper evident). One might also want to log symbolic locationinformation, or to tie this info into contacts, e.g. My Contacts & MyLocations, for commonly used locations.

A “World” mapping application could get auto updates from location. Itactually re-publishes some of the information that may be available froma location server, e.g. time zone and local dialling code. If these werestandardised into location server, the ‘World’ app server could justrelay them through (or perhaps disappear altogether).

5. Power Management—Polling Concerns

Initial usage models will generally assume that location information isonly sought through direct user intervention. This solves many securityand power consumption issues. This has the downside, however, that thetime to first fix (ITFF) could be quite high, as when the user initiateslocation acquisition activity, the device must bootstrap it's knowledgefrom nothing. If any future hardware supports a “tell me when I move(more than X meters)” notification interface, then the TTFN could bereduced significantly. This is based on the assumption the user moves(more than X meters) fairly infrequently in terms of device on time. Fornetwork based location technologies, this could greatly reduce batterydrain for autonomous applications.

6. Architecture—Component Level View

To better understand the architecture, we present a component view basedon areas of responsibility.

The philosophy behind the suggested APIs and Architecture for SymbianLocation Awareness/LBS is:

-   -   “make it easy for most and possible for the others”

Thus, we have the distinction between the different offered APIs and theseparation of plug-ins from the plug-in framework. The overall structureis shown in the attached figure. The main components are described inthe following section.

6.1 Location API

Responsibilities:

Present a clean and simple interface by which most clients can use thelocation primitives offered by the context server. Such an API willprovide the Location primitives to the upper layers of the platform likeapplications, application engines and application protocols.

Offer services to obtain location fixes based on various QoS parametersrequested by its client and present the data in a simple and consistentformat (most likely WGS-84 and possibly Cell-ID strings).

Clients:

-   -   Applications and the application frameworks

Collaborations:

-   -   With the Context Server

6.2 Advanced Location Client API

Responsibilities:

Present a complete and generic interface by which clients can request avariable number of attributes from the Context server and thus make useof any capabilities that a particular location technology may have tooffer. Also allows for bi-directional data transfer.

Clients:

Advanced and/or technology dependent applications and the app framework.

Collaborations:

-   -   With the Context Server

6.3 Location Awareness Server

Responsibilities:

To encapsulate and mediate resource sharing of the location acquisitionresources/technologies. The server is responsible for routing clientcalls to the correct technology plug-in, based on the caller's QOSrequirements, as well as police the interaction based on the platformsecurity model.

It hosts the location acquisition technology plug-ins and provides theframework needed to interface them.

Enforces per transaction policing efficiently so that on every call fromthe client it checks every process' capabilities mask.

Clients:

-   -   The Location Clients

Collaborations:

With the location acquisition technology plug-ins.

-   -   Publish and Subscribe interface in the Kernel.

File Server, DBMS Server

ESock and whatever resources and servers that the technology plugins mayneed.

6.4 Plug-ins Framework Responsibilities:

To enable and facilitate re-use among plug-ins and facilitate plug-indevelopment.

Clients:

-   -   Plug-ins and the Context Server

Collaborations:

-   -   Base components

6.5 Plug-in Message Passing Framework

Responsibilities:

Allow different location acquisition plug-ins to intercept and exchangemessages so that we can have plug-in functionality reuse with loosecoupling (e.g. AGPS using GPS) and for a listen/hook interface in orderto log all events if a product wants it; or for fusion scenarios whereone plug-in may provide location fixes by combining other technologies.

Clients:

-   -   Plug-ins and the Location Server

Collaborations:

-   -   Location Server    -   Base components    -   other plug-ins

6.6 Quality of Position Services

Responsibilities:

Select a positioning technology which fulfils the QoP parametersprovided by a client through the Location Client API. Allow the clientto obtain location fixes without specifying a particular locationacquisition technology plug-in. Basic set of QoP parameters shallinclude: horizontal accuracy, vertical accuracy, time to fix, cost,power consumption.

Clients:

-   -   Plug-ins and the Location Client API

Collaborations:

-   -   Location Server    -   Location acquisition technology plug-ins.

6.7 Location Acquisition Technology Plug-ins

Responsibilities:

To interface with the location acquisition technologies and the LocationServer. Each plug-in is responsible for providing the communicationmechanisms and protocols needed to interface with a particulartechnology and hardware.

Plug-ins are also concerned with providing static technology specificcapabilities, as well as runtime capabilities (e.g. no GPS signal etc)to the server necessary for the location QoS decision making in theserver.

The cost option of a plug-in is provided by the operator/user not theplug-in itself as it may change according to operator, time,subscription and possibly even location (roaming etc).

Clients:

-   -   Location Server and other plug-ins indirectly

Collaborations:

-   -   Context server other plug-ins through the framework    -   ETel (SMS,GSM/GPRS,UMTS)    -   C32 server, UART/some serial or bus abstraction drivers etc.

6.8 Application Framework

Responsibilities:

-   -   Conversion of map data    -   Interfacing to DBMS (e.g. Landmarks DB, persistence, log        viewing)    -   Privacy related settings and service filtering.

Clients:

-   -   Apps and other frameworks.

Collaborations:

-   -   Between Location Server app engines and GUI

7. Client API Recommendations

Location Acquisition Technology Modularity Architecture

In the internal architecture underlying the Location Server the visionis to allow for technology specific server plug-ins to act as thehardware proxies for the location acquisition hardware, utilising theirfull capabilities.

For these reasons and because a varying plethora of such hardware isexpected to be used by licensees and users, the interface between theserver and these plug-in will allow for ‘load time’ capabilitiesdiscovery. In effect a plug-in will present as many published interfacesas it needs.

This can be achieved by making use of a simple capabilities discoveryprotocol and polymorphic factory managed plug-in dlls.

Using this scheme will also allow applications and 3^(rd) parties tomake use of specific hardware capabilities without needing to extend theserver or plug-in interfaces.

As a minimum we believe that the technology plug-ins may exposeinterfaces like:

-   -   NMEA 0183 v2.0 or some subset of    -   Power Management    -   Cell-ID    -   Basic Lon,Lat,Alt    -   Basic Anchor, waypoint operations    -   QoS Capabilities Advertisement

Internally to the technology plug-in modules, developers may choose anynumber of methods to communicate with the hardware. For example toharness all of the device's potential one developer may choose use theproprietary device specific protocols (to communicate with the device)whereas other may decide for time-to-market reasons to use simpler means(like NMEA for GPS receivers). In any case the interfaces exposed willinsulate from the internals that may change in later revisions of thesemodules.

In the case of a 3^(rd) party harnessing the full potential of anadvanced GPS device, they would communicate using the receiver'sproprietary protocol and translate raw data to NMEA sentences as neededif exposing an NMEA interface.

At the same time all modules will be expected to use the ‘Location QoSCapabilities’ interface to register their static and run-timecapabilities with the server (which does not preclude them being storedin a DB). This registration allows the Location Server to dynamicallyselect technology plug-ins to satisfy client requests with particularQoS requirements.

7. Plug-in Settings

Installed Location Server plug-in modules will need a level ofconfigurability that will demand some settings to be stored andretrieved on persistent storage. Configuration of these settings will beexposed to the user by means of control applets.

To achieve a secure and caged access to these settings, they will mostlikely (unless a P&S mechanism is chosen) be stored and structured in adatabse, hosted by the DBMS Server.

A framework for the plug-ins will be provided to access these settingson the DBMS server through the Location Server.

What is claimed is:
 1. An apparatus, comprising: at least one processor,wherein the at least one processor is programmed to cause the apparatusto at least: search for a wireless device with one or more absolutelocation finding systems; request location data from the wirelessdevice, wherein the request includes quality of position parametersselected from at least one of: horizontal accuracy, vertical accuracy,time to fix, cost and power consumption; and receive location data fromthe wireless device.
 2. The apparatus of claim 1, wherein the apparatusis a camera with no absolute location finding system of its own, andwherein the camera is configured to watermark an image with the locationdata.
 3. The apparatus of claim 1, wherein the apparatus is configuredto use the location data to watermark a document or photograph.
 4. Theapparatus of claim 1, wherein the apparatus is further configured toreceive a signature and to watermark the signature with the locationdata.
 5. The apparatus of claim 1, wherein the apparatus is a digitalmusic playing device, and wherein the digital music playing device isconfigured to use the location data to select a song associated with thelocation.
 6. The apparatus of claim 1, wherein requesting the locationdata from the wireless device comprises a request for location contextdata, and wherein receiving location data from the wireless devicecomprises receiving the location context data from the wireless device.7. The apparatus of claim 6, wherein the location context data is speeddata.
 8. The apparatus of claim 6, wherein the location context data istime-zone data.
 9. The apparatus of claim 6, wherein the locationcontext data comprises at least one traffic condition.
 10. An apparatus,comprising: at least one processor, wherein the at least one processoris programmed to cause the apparatus to at least: select an absolutelocation finding system from one or more absolute location findingsystems running on the apparatus that meets quality of position (QoP)parameters defined by an authorized component running on the apparatus;and in response to selecting the absolute location finding system thatmeets the defined quality of position parameters, cause location datafrom the selected absolute location finding system to be sent to theauthorized component running on the apparatus; wherein the QoPparameters are selected from at least one of: horizontal accuracy,vertical accuracy, time to fix, cost and power consumption.
 11. Theapparatus of claim 10, wherein multiple absolute location findingsystems are selected and location data from each selected system isutilized to generate the location data to be sent to the authorizedcomponent.
 12. The apparatus of claim 10, wherein the at least oneprocessor is further programmed to cause the apparatus to receive arequest for the location data and location context data from a wirelessdevice, and send the location data and the location context data to thewireless device.
 13. The apparatus of claim 12, wherein the at least oneprocessor is further programmed to cause the apparatus to determine thelocation data of the apparatus and the location context data associatedwith the location data.
 14. The apparatus of claim 12, wherein thelocation context data is speed data, time-zone data, at least onetraffic condition or a combination thereof.
 15. A method, comprising:searching for a wireless device with one or more absolute locationfinding systems; requesting location data from a wireless device,wherein the request includes quality of position parameters selectedfrom at least one of: horizontal accuracy, vertical accuracy, time tofix, cost and power consumption; and receiving location data from thewireless device.
 17. The method of claim 15, wherein the method isperformed by a camera with no absolute location finding system of itsown, and wherein the method further comprises watermarking an image withthe location data.
 18. The method of claim 15, furthering comprisingusing the location data to watermark a document or photograph.
 19. Themethod of claim 15, further comprising receiving a signature, andwatermarking the signature with the location data.
 20. The method ofclaim 15, wherein the method is performed by a digital music playingdevice, and wherein the method further comprises using the location datato select a song associated with the location.
 21. The method of claim15, wherein requesting the location data from the wireless devicecomprises a request for location context data, and wherein receivinglocation data from the wireless device comprises receiving the locationcontext data from the wireless device.
 22. The method of claim 21,wherein the location context data is speed data.
 23. The method of claim21, wherein the location context data is time-zone data.
 24. The methodof claim 21, wherein the location context data comprises at least onetraffic condition.
 25. A method, comprising: selecting an absolutelocation finding system from one or more absolute location findingsystems running on an apparatus that meets quality of position (QoP)parameters defined by an authorized component running on the apparatus;and in response to selecting the absolute location finding system thatmeets the defined quality of position parameters, sending location datafrom the selected absolute location finding system to the authorizedcomponent running on the apparatus; wherein the QoP parameters areselected from at least one of: horizontal accuracy, vertical accuracy,time to fix, cost and power consumption.
 26. The method of claim 25,wherein selecting the absolute location finding system comprisesselecting multiple absolute location finding systems, and using locationdata from each selected system to generate the location data to be sentto the authorized component.
 27. The method of claim 25, furthercomprising receiving a request for the location data and locationcontext data from a wireless device, and sending the location data andthe location context data to the wireless device.
 28. The method ofclaim 26, further comprising determining the location data of theapparatus and the location context data associated with the locationdata.
 29. The method of claim 26, wherein the location context data isspeed data, time-zone data, at least one traffic condition or acombination thereof.